Problem Note 55869: The third metadata-server cluster node fails to start when you use Quest Authentication Services to enable Integrated Windows Authentication
 |  |  |  |  |
In UNIX operating environments, the third node of a metadata-server cluster might fail to start when you use Quest Authentication Services to enable Integrated Windows Authentication for SAS® Metadata Server.
A notice about the failure appears on the command line immediately after the start-command invocation for the third cluster member. The error does not occur for the first or second cluster members that are started. In addition, the order in which the servers are started does not matter. The error always occurs upon start-up of the third node, which attempts to start and join the cluster.
For the first node, the metadata server starts successfully, as shown below:
$ ./MetadataServer.sh start Waiting up to 600 seconds for Metadata Server to listen to port 8561. Server is started (pid 4713)... Metadata server is responding.
The metadata server also starts successfully for the second node:
$ ./MetadataServer.sh start Waiting up to 600 seconds for Metadata Server to listen to port 8561. Server is started (pid 7562)... Metadata server is responding.
However, for the third node, the metadata server fails to start, and the following error is generated:
$ ./MetadataServer.sh start Waiting up to 600 seconds for Metadata Server to listen to port 8561. Server is started (pid 3542)... *** glibc detected *** /sas94/sashome/SASFoundation/9.4/sasexe/sas: double free or corruption (fasttop): 0x00007f0d54000b40 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x76156)[0x7f0db2447156] /lib64/libc.so.6(+0x78ca3)[0x7f0db2449ca3] /lib64/libc.so.6(+0x7bb70)[0x7f0db244cb70] /lib64/libc.so.6(realloc+0xe5)[0x7f0db244cde5] /opt/quest/lib64/libvas.so.4(vassym_gss_add_oid_set_member+0x88)[0x7f0d60a2c1dc] /opt/quest/lib64/libvas.so.4(+0xf5622)[0x7f0d60a30622] /opt/quest/lib64/libvas.so.4(vassym__gss_load_mech+0x56)[0x7f0d60a306a3] /opt/quest/lib64/libvas.so.4(vassym___gss_get_mechanism+0x11)[0x7f0d60a3105e] /opt/quest/lib64/libvas.so.4(vassym_gss_init_sec_context+0xff)[0x7f0d60a2df71] /opt/quest/lib64/libvas-gssapi.so(gss_init_sec_context+0x8a)[0x7f0d60c667f3] /sas94/sashome/SASFoundation/9.4/sasexe/tksecgss.so(+0x63b4)[0x7f0d60d733b4] /sas94/sashome/SASFoundation/9.4/sasexe/tkiompeb.so(+0xdf363)[0x7f0d62113363] /sas94/sashome/SASFoundation/9.4/sasexe/tkiompeb.so(outcallBind+0x12b5)[0x7f0d6210ddb5] /sas94/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(svcPuddleMain+0x628)[0x7f0d926f4128] /sas94/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(+0x7007e)[0x7f0d9273e07e] /sas94/sashome/SASFoundation/9.4/sasexe/tkiomsvc.so(iomBindURI+0x240)[0x7f0d9273d3e0] /sas94/sashome/SASFoundation/9.4/sasexe/tkiomlb.so(lbConnectToPeer+0x133)[0x7f0d649d4c13] /sas94/sashome/SASFoundation/9.4/sasexe/tkiomlb.so(+0x54004)[0x7f0d649da004] /sas94/sashome/SASFoundation/9.4/sasexe/tkiomlb.so(lbPuddleMain+0x234)[0x7f0d649d6db4] /sas94/sashome/SASFoundation/9.4/sasexe/tkepdl.so(+0x373d)[0x7f0d91bc173d] /sas94/sashome/SASFoundation/9.4/sasexe/tkmk.so(sktMain+0x94)[0x7f0db1c0e214] /sas94/sashome/SASFoundation/9.4/sasexe/tkmk.so(bktMain+0x69)[0x7f0db1c0fdf9] /lib64/libpthread.so.0(+0x79d1)[0x7f0db2e2b9d1] /lib64/libc.so.6(clone+0x6d)[0x7f0db24b9ccd]
The same error might also occur when the SAS® Deployment Wizard configures the third node in a metadata-server cluster. The error occurs when two nodes in the cluster are already running and the third node is being configured.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Metadata Server | 64-bit Enabled AIX | 9.4 | 9.4 | 9.4 TS1M3 | |
| 64-bit Enabled Solaris | 9.4 | 9.4 | 9.4 TS1M3 | |||
| HP-UX IPF | 9.4 | 9.4 | 9.4 TS1M3 | |||
| Linux for x64 | 9.4 | 9.4 | 9.4 TS1M3 | |||
| Solaris for x64 | 9.4 | 9.4 | 9.4 TS1M3 | |||